N4 supports EDIFACT standard COPINO message, release D & version 95B.
The COPINO pre-advise message is provided by inland carriers (railroads, barge operators and trucking companies) to notify the terminal to drop off a container.
This message is to notify the terminal to drop off a container. The EDI messages can be received at any point in the ongoing inbound vessel operation.
The following sections of this document explain how COPINO pre-advise message is handled in N4 and scope of its implementation.
In a terminal, COPINO pre-advise edi is received from the trucking company.
COPINO Inbound Supported Segments
Following table illustrates the segments of EDIFACT standard COPINO D 95B message & scope of each segment in N4.
|
S.No |
Group |
Segment ID |
Supported Qualifier |
Description |
Supported in N4? |
|---|---|---|---|---|---|
|
1 |
|
UNH |
|
Message Header |
Supported |
|
2 |
|
BGM |
|
Beginning of message |
Supported |
|
3 |
|
FTX |
|
Free Text |
Not Supported |
|
4 |
|
RFF |
|
Reference |
Not Supported |
|
5 |
|
TDT |
|
Details of transport |
Supported |
|
6 |
|
LOC |
7 |
Place/location identification |
Supported |
|
7 |
|
DTM |
|
Date/time/period |
Supported |
|
8 |
|
NAD |
MR, MS |
Name and address |
Supported |
|
9 |
|
CTA |
|
Contact information |
Not Supported |
|
11 |
|
GID |
|
Goods item details |
Supported |
|
12 |
|
HAN |
|
Handling instructions |
Not Supported |
|
13 |
|
TMP |
|
Temperature |
Supported |
|
14 |
|
RNG |
|
Range |
Supported |
|
15 |
|
SGP |
|
Split Goods Placement |
Not Supported |
|
16 |
|
DGS |
|
Dangerous goods |
Supported |
|
17 |
|
FTX |
|
Free Text |
Not Supported |
|
18 |
|
EQD |
CN, CH |
Equipment Qualifier |
Supported |
|
19 |
|
RFF |
REO,CAO |
Reference |
Supported |
|
20 |
|
EQN |
|
Number Of Units |
Not Supported |
|
21 |
|
MEA |
|
Measurements |
Supported |
|
22 |
|
DIM |
|
Dimensions |
Supported |
|
23 |
|
SEL |
CA, SH, TO, CU |
Seal number |
Supported |
|
24 |
|
EQA |
|
Attached equipment |
Not Supported |
|
25 |
|
TDT |
|
Details of transport |
Supported |
|
26 |
|
LOC |
9,11, 147 |
Place/location identification |
Supported |
|
27 |
|
DTM |
|
Date/time/period |
Not Supported |
|
28 |
|
NAD |
|
Name and address |
Not Supported |
|
29 |
|
CNT |
|
Control total |
Not Supported |
|
30 |
|
UNT |
|
Message trailer |
Not Supported |
COPINO Inbound - Message Functions
As per EDIFACT standard, COPINO has various message function codes in BGM segment and N4 supports the following message functions are supported
BGM+12+20070702004202+9' – Here "9" is the message function qualifier.
|
Qualifier in the EDI message |
Value in the XML |
|---|---|
|
9 |
O - Original |
|
3 |
D - Cancel |
|
1 |
D - Cancel |
For information on the EDI message functions supported by COPRAR, see Supported EDI message functions (on page 1).
COPINO Inbound N4 Built-in Map
N4 serves a built-in map which is used to convert COPINO edi message into Navis standard preadvise xml. This xml in turn used for further processing.
Following are the related files, part of N4 application and can be downloaded:
copinodropoff_D_95B.mgt - GoXml map
copino.dic - Edifact standard dictionary
preadvise.xsd - Navis standard xml schema
Special Cases
edi:ediInboundVisit mapping
Added a match to SG1 loop (First TDT)
edi:ediOutboundVisit mapping
Added a match to SG5 loop (Second TDT)
N4 has a way of validating some business conditions which might be applicable for some clients and not for some. So those validations are made configurable, the user may turn it on if the particular validation is needed or turn it off if not needed.
The following table lists such configurable settings applicable for COPINO message:
|
Name |
Description |
Edit UI |
Usage |
|---|---|---|---|
|
ARGOPREADVISE001 |
Validate equipment type ISO |
Settings |
To validate the ISO code given in the EDI file. |
|
ARGOPREADVISE002 |
Allow auto creation of foreign vessel visit |
Settings |
To create a vessel if the vessel specified in a COPINO EDI message is not in N4 |
|
ARGOPREADVISE003 |
Validate line operator |
Settings |
To validate the line operator given in the EDI file. |
POD
POD is not given - if the container discharge port is empty system tries to resolve discharge point using the route resolver if defined
If the POD is current port, then the unit category will be considered as "STORAGE"
Line Operator
It uses vessel visit shipping line details to resolve the line operator (Else)
It uses container operator details to resolve the line operator (Else)
Throws error
UNB+UNOA:2+COPTHU+131204+041231:1515+NYK00000000460+++A+1++1'
UNH+NYK00000046001+COPINO:95B:UN+NYK000000460+1:F'
BGM+660+NYK00000046001+9+AB'
TDT+1+TRK001+3++ACME:172:20'
LOC+7+BEANR732+P&O PORTS KADE 732-738'
DTM+132:200708181200:203'
NAD+MS+NYK:172:20'
CTA+IC+:CARRIER'
NAD+MR+NYK:172:20'
CTA+IC+:LUC SIMONS'
GID+1'
FTX+AAA+++LIQUID'
SGP+NSOU0000001'
DGS+IMD+8+1760'
FTX+AAD+++CORROSIVE LIQUID, NOS 5-B?:ROMO-5-NITRO-1,3-DIOXANE'
EQD+CN+ZSPU113245+2200:102:5++2+5'
RFF+CAO:ZSPBKG001'
RFF+CN:ZSP002'
RFF+SQ:1'
MEA+AAE+G+KGM:32300'
SEL+3241+CA+1'
TDT+20+565+1+ZSP:172:20++THU:146::THU'
LOC+9+NZLYT'
LOC+11+HKHKG'
NAD+OCR+UNKNOWN'
CNT+16:1'
UNT+23+NYK00000046001'
UNZ+1+NYK00000000460'